Lifted from the current [jobs generator][]. The only new addition is we
enable the web UI for local development, and configure for [Heroku][].

Since this commit adds a new process, we introduce `Procfile.dev`, and
update `bin/dev` based on [prior art][].

[jobs generator]: https://github.com/thoughtbot/suspenders/blob/main/lib/generators/suspenders/jobs_generator.rb
[Heroku]: https://github.com/sidekiq/sidekiq/wiki/Heroku
[prior art]: https://github.com/rails/jsbundling-rails/blob/main/lib/install/dev

Lifted from existing [views generator][]. Note that we add a new
`app/views/application/_form_errors.html.erb` partial, and no longer
depend on the `title` gem, since Rails ships with a similar solution.

We also do not concern ourselves with any CSS framework (for now).

[views generator]: https://github.com/thoughtbot/suspenders/blob/main/lib/generators/suspenders/views_generator.rb

Lifted from the existing [accessibility generator][].

[accessibility generator]: https://github.com/thoughtbot/suspenders/blob/main/lib/generators/suspenders/accessibility_generator.rb

Lifted from [email generator][]. However, we simplify the implementation
by removing the `include ActiveSupport::Configurable`. Instead, we just
create a simple PORO and place it in `lib`.

[email generator]: https://github.com/thoughtbot/suspenders/blob/main/lib/generators/suspenders/email_generator.rb

Lifted from the existing [inline_svg generator][].

[inline_svg generator]: https://github.com/thoughtbot/suspenders/blob/main/lib/generators/suspenders/inline_svg_generator.rb

Lifted from [development_generator][]. However, we do not need to enable
`annotate_rendered_view_with_filenames` or `query_log_tags_enabled`,
since those are now enabled by default. Also enables
`apply_rubocop_autocorrect_after_generate!` since this is a new option
since the last release.

[development_generator]: https://github.com/thoughtbot/suspenders/blob/main/lib/generators/suspenders/environments/development_generator.rb

…1270)

Lifted from [production generator][]. Also adds the following new
settings:

- Enables [strict_loading_by_default][].
- Sets [strict_loading_mode][] to `:n_plus_one`.
- Enables [sandbox_by_default][].
- Sets [action_on_strict_loading_violation][] to `:log`.

This commit also introduces `ASSET_HOST` and `APPLICATION_HOST`
environment variables.

Finally, since we require the Rails Master Key, we update CI.

[production generator]: https://github.com/thoughtbot/suspenders/blob/main/lib/generators/suspenders/environments/production_generator.rb
[strict_loading_by_default]:
https://guides.rubyonrails.org/configuring.html#config-active-record-strict-loading-by-default
[strict_loading_mode]:
https://guides.rubyonrails.org/configuring.html#config-active-record-strict-loading-mode
[sandbox_by_default]:
https://guides.rubyonrails.org/configuring.html#config-sandbox-by-default
[action_on_strict_loading_violation]:
https://guides.rubyonrails.org/configuring.html#config-active-record-action-on-strict-loading-violation

Prior to this commit, we were getting errors when running `bundle exec
rake install`.

Prior to this commit, we had no specs to test. This commit updates the
CI script by adding a basic static page, and adding a corresponding
system spec.

This revealed we had a broken layout, because we were including a
partial that does not exist.

Currently we do not support the options `-v` or `new` in Suspenders.

In this PR we introduce these two options and deprecating `suspenders
app_name`

Co-authored-by: Steve Polito <spolito@thoughtbot.com>

Makes documentation updates based on rewrite. A future commit could
explore reading from FEATURES.md when creating the generated README.md,
but for now, this works.

Adds notes on how to configure GitHub Actions and Heroku to play nice
with a generated application.

Fix syntax. Since this now actually uses Redis, we needed to update the CI script.

RSpec does not easily distinguish between system and non system tests,
so we just collapse these tasks into one.

Since we enable all the "recommended" RSpec features, we need to ignore
`/spec/examples.txt`, since that feature is enabled.

Alternative to #1261, lifted from the existing [generator][]. However,
since the authoring of that generator, the structure of
`config/environments/test.rb` has changed, so we no longer need
conditionals.

Additionally, we set `action_dispatch.show_exceptions` to `:none` rather
than comment it out to be explicit about the value.

[generator]: https://github.com/thoughtbot/suspenders/blob/main/lib/generators/suspenders/environments/test_generator.rb

Co-authored-by: Rob Whittaker <rob@thoughtbot.com>
Co-authored-by: Jose Blanco <53355525+laicuRoot@users.noreply.github.com>

Follow-up from #1273.

My recommended approach didn't account for calling an invalid command.

There's likely an opportunity to refactor this, but for now, it works.

Testing Suspenders is challenging because it's dependent on the current
version of Rails. Once there's a new release, things can break.

This commit aims to help make local development a little easier by
helping to distinguish code generated by `rails new` from code generated
by the application template.

The previous code was lifted from Staples. Although there wasn't
anything incorrect about it, we don't need a `class` or
`aria-labelledby` attributes. Those can be added as needed.

Add more details to the generated README, as well as the project README.

Introduce binstub to help automate the local QA experience.

…ks (#1288)

This closes #1251.

Since `db:seeds.rb` is intended to ensure

> ... the existence of records required to run the application in every
environment (production, development, test)

we have relied on [`dev:prime`][1] for loading data necessary for users
to view most of the features of the app in development.

However, there were a few areas of improvement.

First, rename `dev` namespace to `development`, and rename [`prime`][1]
task to `seed` for improved clarity.

Then, introduces `development:db:seed:replant` take to create parity
with the existing `db:seed:replant` task.

Introduces `Development::Seeder` class to encapsulate seed data, which
is called in the `development:db:seed` and `development:db:seed:replant`
tasks. The advantage to this is that the class can be called
independently from the task, and can also be [unit tested][2].

Finally, we ignore this class from being auto-loaded, since it's
intended for development use.

[1]: https://thoughtbot.com/blog/priming-the-pump
[2]: https://thoughtbot.com/blog/seeds-of-destruction

Add documentation, update release notes, bump version and run `bundle
exec rake build`.